V1.1
  Fixed the special feature for 64drive users so it works correctly regardless what version bootloader you're using.
  Make sure you either set the menu option to reset to game or hold start while the game resets.

  PJ64 2.x now confirmed supported by adding a single NULL nyte into its internal name, under duress.
  As of at least June 2020, mainline PJ64 generates filenames for saves, etc. using the internal name from the header.  They start reading at 0x20 and continue until they hit a NULL byte, then push whatever that string is out raw without sanitizing it or accounting for encoding.  This is why it mutilates the ~48 Japanese titles that use codepage 932 (or whatever else you want to call that SJIS IBM offshoot), and mutilates it in different ways depending on your OS's nonunicode default encoding.
  This wouldn't be a problem since there's a range of bytes that's reserved for a future use that never occurred, but I kinda insert a timestamp into those so minor release revisions are easier to sort out on my end and yours.  That said, pushing an unsanitized string as a filename is a possible exploit vector for your OS.

  Everdrive v2.x and v3 are confirmed working, but Everdrive X7 is confirmed *broken*.  Several of my previous patches also will not run as expected or crash on X7s due to address conflicts primarily with 64drive features.  This is confirmed for, but is likely not limited to, the Densha de Go 64! (USA) and Bomberman64 (USA) translations.
  There is no plan for a fix.  Reverse-engineering yet another version of this device doesn't sound very appealing.

-Zoinkity

